Method for generating customer secure card numbers

ABSTRACT

A method for providing secure transactions generates a Secure Card Number (“SCN”) for a first entity that is transferred with a first entity identifier to a second entity and then to a money source that verifies that the transaction is valid by use of the first entity identifier and the SCN. The SCN includes a 0Transaction Information Block (“TIB”), a Counter Block, and an encrypted Personal Identification Number (“PIN”) Block. The SCN is transferred to the money source in an account number or a non-account data field. The money source can use the TIB to determine whether the SCN should be used once or multiple times or to identify one of several physical devices, all of which are issued to the first entity, used to generate the SCN. The money source validates the SCN by duplicating the encryption process used to create an encrypted PIN Block and comparing the result to the encrypted PIN Block received with the transaction. A Triple Data Encryption Standard algorithm encrypts a PIN Block generated from a PIN, a Sequence Insertion Number (“SIN”) and a known starting value. The SIN can be a combination of three seed values and a random value generated by a Pseudo Random Number Generator (“PRNG”) initialized with the seed values. A Counter value is associated with the Counter Block and the seed values.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is related to U.S. application Ser. Nos.09/667,081 and 09/667,089, filed Sep. 21, 2000, which arecontinuation-in-part applications of U.S. Ser. No. 09/659,434, filedSep. 8, 2000, which is a continuation-in-part of U.S. Ser. No.09/640,044, filed Aug. 15, 2000, which is a continuation-in-part of U.S.Ser. No. 09/619,859, filed Jul. 20, 2000, which is acontinuation-in-part of U.S. Ser. No. 09/571,707, all of whichdisclosures are specifically incorporated herein by reference. Thisapplication is also related to another application being filedconcurrently herewith, entitled Method for Generating Customer SecureCard Numbers Subject To Use Restrictions By An Electronic Card, Ser. No.09/960,714.

FIELD OF THE INVENTION

The present invention is in the field of payment systems.

BACKGROUND OF THE INVENTION

Three forms of money in widespread use today throughout the world arecash, checks and payment cards (debit or credit). Each has distinctadvantages, and distinct disadvantages. Cash is readily accepted, easyto use and anonymous, but it does not earn interest, it can be lost orstolen, and it is not always readily accessible. Checks are not alwaysaccepted, but they offer many advantages, since they do not have to bewritten until the time of payment. However, they must be physicallypresented and they are not anonymous. Payment cards are readily, but notalways, accepted, and they offer many advantages over checks. If thecard is a credit card, payment can be deferred, but the transaction isnot anonymous. If the card is a debit card, payment has usually beenmade prior to its use, but it is anonymous. Accordingly, it is apparentthat different types of money have different advantages to differentpersons in different situations. This may be one reason why all theseforms of money are still in widespread use, and are even used by thesame persons at different times.

As society and international commerce have become more dependent uponelectronic transactions, money has also become more electronic. Manyattempts have been made to come up with suitable forms of electronicmoney that mimic the physical world, or even create new forms ofelectronic money. However, despite the enormous need for such money, andefforts by some of the best minds and most successful companies in theworld, electronic money has suffered many setbacks and been far slowerto materialize than many had hoped or predicted. The reasons are manyand varied, but some of the obvious reasons are security, ease ofuse/operation, and unwillingness of the public and/or commerce to makeradical changes or embrace new technology and/or procedures. As aresult, many efforts, including several potentially promising efforts,have met with failure.

Even though new forms of electronic money have been slow to develop orgain widespread acceptance, electronic payments have still movedforward. Many banks now offer some form of electronic checking. Andpayment cards have been used for electronic transactions in e-commerceand m-commerce (mobile commerce). Still, there is widespread concernabout the safety of such transactions, and recent news stories haveuncovered widespread fraudulent activity associated with use oftraditional credit card numbers in e-commerce over the Internet. Inaddition, there is growing concern about consumer privacy, or lackthereof, due to widespread electronic profiling of consumers who makeelectronic payments.

Although the media has been quick to cover fraud associated with use ofcredit cards over the Internet, it is often overlooked, at least by thepublic and the media (but not the credit card companies), that themajority of fraudulent activity concerning credit cards is notassociated with e-commerce activity. Most fraud occurs in the “brick andmortar” world, and the numbers are daunting. Despite many attempts tocombat unauthorized or fraudulent use of credit cards, it is estimatedthat credit card fraud now exceeds hundreds of millions, if not severalbillion, dollars per year. And this does not even count the cost ofinconvenience to consumers, merchants and credit card issuer/providers,or the emotional distress caused to victims of such fraud, or the costto society in terms of law enforcement and preventative activities.

Accordingly, there is a very real, long-felt need to reduce the amountof fraudulent activity that is associated with credit cards, and thisneed has only grown more acute as consumers and commerce search forbetter ways to purchase and sell goods and services via e-commerce andm-commerce. However, any solution needs to be something that isacceptable to the public at large. It should be easy to use. It shouldnot be complicated or expensive to implement. Preferably, it should fitwithin the existing infrastructure, and not be something that requires agreat deal of educational effort, or a radical change in behavior orhabits of consumers. In other words, it should be user friendly, readilyunderstandable and something that does not require a completely newinfrastructure, which is a reason suggested by some as to why smartcards have not been widely accepted in the United States.

In addition, it is highly desirable that any solution to such problemsbe capable of widespread use, in many different platforms, for manydifferent applications.

In U.S. Pat. No. 5,956,699 issued in September of 1999, Wong andAnderson were the first to introduce the methodology of a system forsecure and anonymous credit card transactions on the Internet. Thispatent introduced a system which used an algorithm to use one's ownselected Personal Identification Number (PIN) as one's own de factodigital signature. The algorithm instructs the cardholder how to insertone's PIN into one's valid credit card number before using it for anytransactions on the Internet. The resultant scrambled up credit cardnumber, which is tailored by the algorithm to having the same number ofdigits as before, is rendered useless on the Internet because the PINinsertion algorithm is changed automatically after every transaction.This methodology is not only capable of drastically reducing credit cardfraud on the Internet, it is also capable of safeguarding one'sanonymity, and thus privacy, in credit card purchases on the Internet.

After the issuance of U.S. Pat. No. 5,956,699, Wong et al. also inventedan anonymous electronic card for generating personal coupons useful incommercial and security transactions, a method for implementinganonymous credit card transactions using a fictitious account name, aswell as methods for generating one-time unique numbers that can be usedin credit card transactions in the brick and mortar world, e-commerce,m-commerce and in many other applications.

The present invention seeks to provide new methods for generating andprocessing Secure Card Numbers (SCN) that can be used in all types oftransactions in which a conventional credit card account number isaccepted. In addition, the present invention conforms to the existingstandards for PIN encryption as promulgated by the American BankersAssociation (ABA), the American National Standards Institute (ANSI), theInternational Standards Organization (ISO), and the Federal InformationProcessing Standards (FIPS) Publications of the National Institute ofStandards and Technology (NIST). Because the methodology is well suitedfor use in hardware and software applications, it has widespreadapplicability to many different types of transactions.

The present invention is related to the concept of customer one-timeunique purchase order numbers (“Coupons”) as described in U.S. Ser. No.09/640,044. An algorithm is executed that uses a user account number, acustomer sequence number, a customer permutated user key, and aTransaction Information Block (TIB) as input variables to form an SCNthat is correlated with a sequence number. Combining a user key with auser account number, a user insertion key correlated with the customersequence number, and then encrypting the result using the Triple DataEncryption Standards (TDES), forms the customer permutated user key. Arandom number generator generates the user insertion key that iscorrelated with the sequence number. The TIB may provide several piecesof information, including the conditions under which the SCN will bevalid (i.e., the SCN type), additional account indentificationinformation, and the status of the device used for SCN generation. Thesequence number can be changed after each SCN is generated and a new SCNcan then be generated using a new user insertion variable correlated tothe changed sequence number.

After an SCN is generated, it is transferred with a first entityidentifier to a second entity (which can actually be several entities),which then transfers the information to a money source. An individualSCN is verified as being valid by the money source by duplicating thegeneration of the customer permutated user key for the specified firstentity and the specified sequence number, and then comparing it to thecustomer permutated user key which is embedded in the provided SCN.Additionally, the money source verifies that the specified SCN type isvalid given the specific conditions of the transaction. Once verified asvalid, each SCN passes through a life cycle in accordance withconventional credit card processing practices and with its SCN type, inwhich it may be used for various types of transactions before beingretired. If a preselected number of SCNs are received by the moneysource and determined to be invalid (either consecutively or within apredetermined timeframe), then an invalid user account number conditionis set to prevent further attempts to verify SCNs for that first entity.

A user key can be entered into an input device, and validates the userkey by comparing it to a stored user key. If the entered user key isvalid, the user can generate an SCN. The sequence number changes eachtime a user key is entered into the input device.

SUMMARY OF THE INVENTION

The present invention is generally directed to a method for providingone or more secure transactions between a first entity and at least oneadditional entity in which a Secure Card Number (“SCN”) is generated forthe first entity, then transferred with a first entity identifier to asecond entity and then transferred to a money source that verifies thatthe transaction is valid by use of the first entity identifier and theSCN. The SCN includes a Transaction Information Block (“TIB”), a CounterBlock, and an encrypted Personal Identification Number (“PIN”) Block.The SCN can be transferred to the money source in an account numberwhile the first entity identifier is transferred to the money source ina non-account data field or the first entity identifier can betransferred to the money source as an account number while the SCN istransferred to the money source in a non-account data field.

In a first, separate aspect of the present invention, the TIB can beused for invoking one or more restrictions on use of the SCN. The moneysource can use the TIB to determine whether the SCN should be asingle-use SCN (i.e., can only be used for a single transaction by thefirst entity) or a multiple-use SCN (i.e., can be used for multipletransactions between the first entity and a single merchant). The TIBcan also be used by the money source to identify the physcial deviceused to generate the SCN.

In another, separate aspect of the present invention, the money sourcevalidates the SCN by duplicating a PIN Block encryption process used tocreate the encrypted PIN and by then comparing the result to theencrypted PIN Block received with the transaction.

In still another, separate aspect of the present invention, theencrypted PIN Block is formed by using a Triple Data Encryption Standardalgorithm (“TDES”) to encrypt a PIN Block. The PIN Block can begenerated from a PIN associated with the first entity, a SequenceInsertion Number (“SIN”) and a starting value known to both the firstentity and to the money source. The SIN can be a combination of a firstset of seed values and a random value generated by a Pseudo RandomNumber Generator (“PRNG”) that was initialized with the first set ofseed values. The first set of seed values is associated with a Countervalue that is associated with Counter Block.

In yet another, separate aspect of the present invention, when the SCNis a nine digit number, the TIB is a one digit number, the Counter Blockis a four digit number, and the encrypted PIN Block is a four digitnumber. The encrypted PIN Block can be created by dividing an 8-byteSequence Insertion Number (“SIN”) into four 2-byte integers (three seedvalues and the random number), adding the PIN and a pre-assignedconstant 4-digit value to each of the four 2-byte integers,concatenating the results to form an 8-byte input block which the TDESencrypts into an 8-byte output block, dividing the 8-byte output blockinto four 2-byte integers x1, x2, x3 and x4 and then using integersx1–x4 to produce the 4-digit encrypted PIN Block with a value P, whereinP=(Ax1+Bx2+Cx3+Dx4) mod 10000, each of the values A, B, C and D beingpre-assigned odd integers.

Accordingly, it is a primary object of the present invention to providea method for generating and processing customer Secure Card Numbers foruse in transactions where conventional credit card numbers are accepted.

This and further objects and advantages will be apparent to thoseskilled in the art in connection with the detailed description of thepreferred embodiment set forth below.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 illustrates a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is related to U.S. Pat. Nos. 5,913,203, 5,937,394and 5,956,699, the disclosures of which are all specificallyincorporated herein by reference.

The preferred embodiment of the present invention is adapted for use incredit card transactions, and as such can be used in connection with awide variety of instruments that can be used in connection with suchfinancial transactions: electronic cards, software programs used innetwork applications, telephones (especially telephones used in what isnow being referred to as m-commerce, or mobile commerce), or evenphysical imprint transactions. Moreover, it can be used whether suchtransactions are conducted in person, face-to-face, or whether suchtransactions are conducted by an indirect medium, such as a mail ordertransaction, a transaction conducted over a computer network (forexample, the Internet), or a telephone transaction.

As is the case in most financial transactions, three parties aretypically involved in completed credit card transactions according tothe present invention. A party presents a credit card account numberwith the intent to initiate a monetary payment (or credit/return). Inthe context of the following description, this is the first entity orcustomer. Another party receives the credit card account number with theintent to receive a monetary payment (or credit/return), and this partycan be a single party or two or more parties. In the context of thefollowing description, the party or parties that are receiving thecredit card account number are referred to as the second entity ormerchant. Finally, there is at least one party, and usually multipleparties, that serve as intermediaries to the monetary payment (orcredit/return). The second entity provides the credit card accountnumber to this party over several transactions to effect the monetarypayment (or credit/return): authorization, incremental authorization,authorization reversal, settlement, and credit/return. The intermediarygroup of one or more parties will be referred to in the context of thefollowing description as a money source. Thus, the money source may beone or more banks, a credit card company or any other institutioninvolved with issuance of credit cards or bank debit cards, such as acredit union or other institution, or a money source as described inU.S. Pat. No. 5,913,203.

In connection with the preferred embodiment, it is not necessary thatthe first entity use a real identity, although such an option is alsoacceptable. Instead, a pseudonym, such as a screen name or an alias,could be used to protect the first entity's privacy and provideadditional security.

Although the first entity need not use a real identity, the first entitymust establish an account with a money source. When the account isestablished, the first entity and the money source must agree upon apayment mechanism or protocol. In the case of a credit card or a bankcard, this could be done in the same fashion as exists today, and thefirst entity could select a fictitious account name as is explained ingreater detail in co-pending U.S. patent application Ser. No.09/619,859. It is especially preferred that two different users not beallowed to select the same fictitious account name so that a fictitiousaccount name also represents a unique identifier. However, the preferredembodiment could also be used in connection with a prepaid account. Insuch a scenario, the first entity could simply purchase a prepaid cardand no real identity would ever be required.

When the first entity establishes an account with the money source, auser key must be selected. The user key can be a PIN, similar to thatwhich is currently in widespread use in the United States in connectionwith automated teller machines. Both the first entity and the moneysource must have access to the user key, which can be selected by eitherentity. In order to be able to retrieve this user key, the money sourcemust create a record associated with the first entity that includes theuser key and a first entity identifier (whether this be the real name ofthe first entity or a fictitious account name).

Once the first entity has established an account with the money sourceand a user key has been selected, the first entity must be supplied withthe means to generate a customer SCN. As already described, this couldbe hardware or software, but in either case it will include a useraccount number, a customer random number generator that will be used togenerate user insertion keys that are correlated with a customersequence number, and TDES encryption keys.

The TDES encryption standard is the accepted standard for protecting aPIN during data transmission of financial transactions, as described byISO 9564-1-1991 (Banking—Personal Identification Number Management andSecurity—PIN Protection Principles and Techniques, Section 6.2), ISO9564-2-1991 (Banking—Personal Identification Number Management andSecurity—Approved Algorithms for PIN Encipherment), ANSI X9.52-1998(Triple Data Encryption Algorithm—Modes of Operation), and FIPS PUB 46-3(Data Encryption Standard (DES), dated 1999), the disclosures of whichare specifically incorporated herein by reference.

In order to effectively use TDES for PIN encryption, the PIN must becombined with a new set of randomly generated data for each transaction.Otherwise, the encrypted PIN would always be the same value. A customerrandom number generator, such as the one that is described in U.S.patent application Ser. No. 09/640,044, filed Aug. 15, 2000 and which isgenerally known as a Linear Congruential Generator (LCG), is used forthis purpose. This random number generator is algorithmic (i.e.,pseudo-random)—when starting with the same set of seeds, it alwaysproduces the same sequence of numbers. It can therefore be reproduced bythe money source in order to validate a given SCN. Furthermore, sincethis pseudo random number generator generates its values in areproducible sequence, each of the values in the sequence can beidentified by a Counter value that indicates that number's location inthe sequence. The set of random numbers generated and combined with thePIN are collectively referred to as the Sequence Insertion Number (SIN).

In the real world of credit card transactions, it is not possible toassume that transactions conducted by the first entity in a given orderwill always be received by the money source in that same order.Therefore, the money source method of SCN validation must be based on anembedded sequence value. The Counter value is used for this purpose inthe preferred embodiment.

In general, this method can be used to generate SCNs of many differentlengths. In the conventional credit card processing infrastructure, acredit card number is typically 16 digits in length. Such a numbercomprises three subnumbers: a 6 digit Bank Identification Number (BIN),a 9-digit account number, and a 1-digit checksum number. For the purposeof being compatible with the existing credit card processinginfrastructure, the SCN could be 9 digits in length, and could take theplace of the account number in the conventional 16-digit credit cardnumber.

In the preferred embodiment, the 9-digit SCN itself comprises threesubnumbers: a 1 digit TIB, a 4 digit Counter Block (which identifies therandom number being used for encryption), and a 4 digit encrypted PINBlock.

The 1 digit TIB may take on up to 10 different values, each of which mayindicate multiple pieces of information. The TIB can be used todetermine which of a plurality of account numbers associated with thefirst entity should be used for the first transaction. The accountnumbers can represent, for example, different credit card accounts ordifferent payment or credit cards. A first account number might beassociated with the TIB value of 0, a second account number might beassociated with the values of 1 and 2, a third account number might beassociated with values of 3 and 4, and so forth, wherein any odd valuemay be restricted to a one transaction limitation while any even valuemay be used to invoke permission for multiple transactions at a singlemerchant. In the preferred embodiment, a TIB value of 0 indicates thatthe SCN may only be used for one transaction; any attempts to use it forsubsequent transactions will result in a transaction denial from themoney source. A value of 1 indicates the same transaction restrictionsas 0, but also indicates that the device generating the SCN has a lowbattery power condition. A value of 2 indicates that the SCN may be usedfor multiple transactions, but only at a single merchant; any attemptsto use it for subsequent transactions at a different merchant willresult in a transaction denial from the money source. A value of 3indicates the same transaction restrictions as 1, but also indicatesthat the device generating the SCN has a low battery power condition.Furthermore, a set of TIB values (4, 5, 6, 7) might represent the samerestriction and status information as (0, 1, 2, 3), respectively, butfurther indicate that the transaction is associated with a differentsubentity (e.g., the first entity identifier identifies a marriedcouple, and the TIB identifies each individual spouse.) Other valuesmight also be used to enforce additional transaction restrictions inways readily apparent to those skilled in the art.

The TIB can also be used by the money source to uniquely identify aphyscial device (such as an electronic card) used to generate the SCN.This aspect of the TIB is especially useful when the money source issuesmore than one card to a first entity. Multiple cards might be issued tothe same person (i.e., the first entity) for different uses, or multiplecards might be issued to the same person for use by differentindividuals (such as family members). In such instances, the TIB canidentify which physical card, issued to the first entity, is used for agiven transaction. When the TIB is used in this way, the TIB can be usedas a customization variable to recognize multiple cards otherwise issuedto a single first entity (which might also be a legal entity, such as acorporation).

The 4-digit Counter Block is unencrypted information provided so thatthe money source may decrypt and validate the SCN. It may be simply theactual Counter value (incremented after each use), but in the preferredembodiment, it is created by adding the Counter value to a startingvalue known to both the first entity and to the money source.

The 4-digit PIN Block is the encrypted information that is used tovalidate the fact that the SCN originated from the first entity. The PINBlock is formed using the PIN, the SIN, and a starting value known toboth the first entity and to the money source. It is encrypted usingTDES, which requires use of three 64-bit keys known to both the firstentity and to the money source. In order to encrypt such a small number(16 bits) with such a high level of encryption (158 bits), the PIN mustfirst be expanded to a 64 bit number, then encrypted, and finallyreduced back to a 16 bit number—and in such a way that it is guaranteedto be different for each transaction.

The SIN is the product of an LCG random number generator that isinitialized with three 2-byte integer seeds—the result of operating theLCG on these seeds is a 2-byte random value. The 8-byte SIN consists ofthe three seeds plus the random value. As a by-product of its operation,the LCG also produces three new seeds, which will be used for the nextiteration of the LCG algorithm. The SIN may therefore be associated witha Counter value that indicates a unique location in the sequence ofseeds and value generated by the LCG. This SIN is used as the randombasis for each successively TDES-encrypted PIN Block, and guarantees aproperly encrypted PIN Block for each transaction. To allow propervalidation of the SCN, the Counter value stored in the Counter block isthe one associated with the SIN used as the random basis for the PINBlock.

The creation of the PIN Block starts by dividing the 8-byte SIN intofour 2-byte integers. The PIN and a predefined constant value are bothadded to each individual 2-byte integer. The results are thenconcatenated back again to form an 8-byte input block to the TDESalgorithm, which encrypts them into an 8-byte output block. The outputblock is then divided back into four 2-byte integers (x1, x2, x3, x4).These four values are then used in the following formula to produce the4-digit PIN Block value P:

F o r m u l a  1:P R N G  V a l u e  C a l c u l a t i o nP = (A x₁⁺B x₂⁺C x₃⁺D x₄)m o d 10000In this formula, the four values (A,B,C,D) are each odd integers. The“mod” calculation is a standard modulo arithmetic operation, and worksas follows: if the resulting number is greater than 10,000 (or 20,000 or30,000, etc.), then the value of 10,000 (or 20,000 or 30,000, etc.) issubtracted from it, leaving a positive four digit value.

Once created, the SCN is transmitted along with the first entityidentifier from the first entity to the second entity and, subsequently,to the money source. In one embodiment, the SCN is used in an accountnumber that replaces the conventional credit card number, and the firstentity identifier is a static 9 digit number pre-assigned to the firstentity that is transferred to the money source in a non-account datafield. In the case of an electronic swipe credit card transaction, thefirst entity identifier is dynamically encoded onto Track 1 and/or Track2 of the magnetic stripe in the area known as the Discretionary DataField, which comprises up to 13 digits of information. In the case of atransaction where the first entity is not present, such as a mail order,telephone order, or Internet order, the first entity identifier istransmitted as part of the Billing Address field in one of may possibleforms. For example, it may be entered as “P.O. Box<first-entity-identifier”.

In an especially preferred embodiment, the SCN is not used in an accountnumber to replace the conventional credit card number, but is insteadused in conjunction with it—the conventional credit card number itselffunctions as the first entity identifier, and the SCN is used as adynamic digital signature to positively identify the first entity and istransferred to the money source in a non-account field of data. In thiscase, the SCN is transmitted either in the Discretionary Data Field ofTrack 1 and/or Track 2 or via the Billing Address in a card-not-presenttransaction.

The Money Source validates the SCN by using the first entity identifierto lookup the information necessary to reproduce the PIN Blockencryption for the first entity: the TDES keys, the LCG Seeds, and thePIN. The Money source determines the Counter value by examining theCounter Block, reproduces the calculation of the PIN Block, and thencompares the results to the received PIN Block to perform the actualvalidation.

The Money Source also validates the usage of the SCN based on theembedded TIB. It therefore enforces the various policies based on thefirst entity's previous transaction history: single-use, multiple-usefor single merchant, card-present only.

In the embodiment when the SCN is used in an account number in place ofthe conventional credit card number, it passes through the standardcredit card transaction life-cycle: initial authorization, potentialincremental authorization, potential authorization reversal, settlement,and potential credit/return. However, in an especially preferredembodiment, the SCN is only used for initial authorization—beyond that,the Money Source performs its standard transaction processing.

The Money Source may detect fraudulent transaction attempts in variousways. In both the embodiment where the SCN replaces the conventionalcredit card number, the Money Source may check for re-use of single-useSCNs, use of SCNs without first entity identifiers when the card is notpresent, re-use of multiple-use/single-merchant SCNs at a differentmerchant, or SCNs with invalid PIN Blocks. Each of these casesrepresents a different type of fraud. The Money Source may take variousactions in response to each of these types of attacks, such as disablingthe account after an excessive number of fraudulent transactionattempts, or returning the code indicating that the merchant shouldretain the credit card being used for the transaction.

In the preferred embodiment, the Money Source detects fraudulentauthorization attempts such as re-use of single-use SCNs, re-use ofmultiple-use/single-merchant SCNs at a different merchant, SCNs withinvalid PIN Blocks, or use of the conventional credit card number on anSCN-enabled account without inclusion of an SCN when the card isnot-present. This last case covers simple Internet fraud attempts, butallows, for example, a manual-entry transaction at a POS machine or animprint transaction. After detecting fraud attempts, the Money Sourcemay take the same types of actions as described above.

It should be noted that the preferred embodiment allows the SCN, whenpaired with a conventional credit card number, to be validated byback-end software that is integrated with the issuing money source'sauthorization and settlement processing. An issuing money source canidentify an SCN-enabled credit card account in an issuer-determinedfashion (e.g., a unique Bank Identification Number). It then forwardsselect transaction information to the SCN-enabling software, which isinstalled behind the issuing money source's firewall, which validatesthe SCN. This means that software generating the SCN can be allowedoperate in isolation—it does not have to be in communication with theback-end software—and thus it can be embedded in a credit card or otherstandalone device.

The inventions described above can be implemented by a money source foruse with an electronic card. It is preferable that every user accountutilizes the same Pseudo Random Number Generator (PRNG), such as thePRNG described in P. L'Ecuyer, “Efficient and Portable Combined RandomNumber Generators”, Communications of the ACM, 31(6):742-749,774, 1988,the disclosure of which is specifically incorporated herein byreference. However, each cardholder account has a different initialseed, and thus uses a different part of the PRNG sequence. Since thePRNG has an overall period of 10¹², there is ample room for each accountto have its own non-repeating subsequence of 10,000 values.

The PRNG is divided into two parts: seed generation (Formula 2) andvalue calculation (Formula 3). In these formulas (expressed using C codefragments), the set (S_(x) ⁰, S_(x) ¹, S_(x) ²) is a triplet offive-digit values in the range ([1,32362], [1,31726], [1,31656])), andrepresents the seed in the x^(th) location in the sequence. Z is interimstorage for the pseudo random number, and PRNG[x] indicates the pseudorandom number in the x^(th) location in the sequence. Note that for thepractical usage of this algorithm, “x” corresponds to the currentCounter value. For each transaction, Formula 2 generates the seed (basedon the previous seed) and Formula 3 generates the PRNG value.

F o r m u l a  2:P R N G  V a l u e  C a l c u l a t i o nZ = S_(x)⁰ − S_(x)¹; i f  (Z > 706)Z = Z − 32362; Z = Z + S_(x)²;i f  (Z < 1)Z = Z + 32362; P R N G[x] = ZFormula  3 : PRNG  Seed  Genaration $\begin{matrix}{S_{x_{1}}^{0} = {( {S_{x - 1}^{0}*157} )\mspace{14mu}{mod}\mspace{14mu} 32363}} \\{S_{x_{2}}^{0} = {( {S_{x - 1}^{1}*146} )\mspace{14mu}{mod}\mspace{14mu} 31727}} \\{S_{x}^{2} = {( {S_{x - 1}^{2}*142} )\mspace{14mu}{mod}\mspace{14mu} 31657}}\end{matrix}$

In all cases, the initial PRNG seed (which generates value 0 in the PRNGsequence) is pre-assigned to the card. Additionally, the most recentlyused seed is stored in Random Access Memory (RAM). Thus, when an SCNmust be generated, the card runs through both Formulas 2 and 3 exactlyonce, and then updates the seed storage in RAM. The Counter value isalso stored in RAM, and is initialized to the value of 1 at the time thecard is manufactured. Multiple values of the Counter are stored todetect accidental corruption. Each time an SCN is generated, the currentvalue of the Counter is used. The Counter is then incremented by 1, andstored again for the next use.

Since the SCN is calculated in an algorithmic fashion, it is possible toprecalculate the values for a given first entity, and store them on anelectronic card. This embodiment is most useful where it is moreadvantageous to store a large amount of data on the electronic card thanit is to perform the algorithms discussed above.

Use of the SCN technology described herein is secure when it requiresthe cardholder to enter a PIN in order to generate a unique SCN that isvalid for only one transaction, and for only the specified cardholder.At no time during the transaction is the PIN at risk. By utilizing bothencryption and random number generation technologies described herein,it is possible to achieve at least a 99.9% level of protection againstfraud.

Although the foregoing detailed description is illustrative of preferredembodiments of the present invention, it is to be understood thatadditional embodiments thereof will be obvious to those skilled in theart. For example, the same inventive concepts disclosed herein could beused in a system in which a customer has two or more account numbersand/or identities, with the same or different user keys. In the case ofan electronic card or telephone, this would allow the customer to selectwhich account should be used (for example, to choose a business creditcard for use with a business expense, a personal credit card for usewith a personal expense, or a bank card at a local store for groceriesand cash back). Alternatively, a customer might be permitted to usemultiple user keys for the same account number and the same identity.This could allow some of the same functionality, or it could be used toclassify the type or nature of the expense or transaction. Furthermore,the same SCN concept can be easily extended to non-financialtransactions where user authentication is required, such as withelectronic Identification cards. Further modifications are also possiblein alternative embodiments without departing from the inventive concept.

Accordingly, it will be readily apparent to those skilled in the artthat still further changes and modifications in the actual conceptsdescribed herein can readily be made without departing from the spiritand scope of the disclosed inventions as defined by the followingclaims.

1. A method for providing one or more secure transactions between afirst entity and at least one additional entity, comprising the stepsof: (1) generating a Secure Card Number (“SCN”) for the first entity,wherein the SCN is comprised of: (a) a Transaction Information Block(“TIB”); (b) a Counter Block; and (c) an encrypted PersonalIdentification Number (“PIN”) Block; (2) transferring the SCN and afirst entity identifier to a second entity in a first transaction; (3)transferring the SCN and the first entity identifier from the secondentity to a money source; and (4) verifying that the first transactionis valid with the money source by use of the first entity identifier andthe SCN.
 2. A method as recited in claim 1, wherein the SCN istransferred to the money source in an account number and the firstentity identifier is transferred to the money source in a non-accountdata field.
 3. A method as recited in claim 1, wherein the first entityidentifier is transferred to the money source as an account number andthe SCN is transferred to the money source in a non-account data field.4. A method as recited in claim 3, wherein the TIB is used for invokingone or more restrictions on use of the SCN.
 5. A method as recited inclaim 4, wherein the TIB is used by the money source to determinewhether the SCN is a single-use SCN or a multiple-use SCN.
 6. A methodas recited in claim 5, wherein the TIB is used by the money source toidentify a physical device used to generate the SCN.
 7. A method asrecited in claim 6, wherein the encrypted PIN Block is formed by using aTriple Data Encryption Standard algorithm (“TDES”) to encrypt a PINBlock.
 8. A device as recited in claim 7, wherein the PIN Block isgenerated from a PIN associated with the first entity, a SequenceInsertion Number (“SIN”) and a starting value known to both the firstentity and to the money source.
 9. A method as recited in claim 8,wherein the SIN is a combination of a first set of seed values and arandom value generated by a Pseudo Random Number Generator (“PRNG”) thatwas initialized with the first set of seed values.
 10. A method asrecited in claim 9, wherein the first set of seed values consists ofthree seed values.
 11. A method as recited in claim 10, wherein thefirst set of seed values is associated with a Counter value.
 12. Amethod as recited in claim 11, wherein the Counter Block is associatedwith the Counter value.
 13. A method as recited in claim 12, wherein themoney source validates the SCN by duplicating a PIN Block encryptionprocess used to create the encrypted PIN and by then comparing theresult to the encrypted PIN Block received with the first transaction.14. A method as recited in claim 13, wherein the SCN is a nine digitnumber, the SCN Type is a one digit number, the Counter Block is a fourdigit number, and the encrypted PIN Block is a four digit number.
 15. Amethod as recited in claim 14, wherein the encrypted PIN Block iscreated by dividing an 8-byte Sequence Insertion Number (“SIN”) intofour 2-byte integers, adding the PIN and a pre-assigned constant 4-digitvalue to each of the four 2-byte integers, concatenating the results toform an 8-byte input block which the TDES encrypts into an 8-byte outputblock, dividing the 8-byte output block into four 2-byte integers x1,x2, x3 and x4 and then using integers x1–x4 in Formula 1 to produce the4-digit encrypted PIN Block with a value P, wherein Formula 1 isP=(Ax1+Bx2+Cx3+Dx4) mod 10000, each of the values A, B, C and D beingpre-assigned odd integers.
 16. A method as recited in claim 15, whereineach of the three seed values and the random value is a 2-byte integer.17. A method as recited in claim 16, wherein an electronic cardgenerates the SCN.
 18. A method as recited in claim 16, wherein a PIN isentered into an input device to generate the SCN.
 19. A method asrecited in claim 18, wherein the SCN and first entity identifier aretransferred to the second entity in a form.
 20. A method as recited inclaim 19, wherein the SCN is transmitted through an Address VerificationSystem Billing Address.
 21. A method as recited in claim 20, wherein aunique SCN is assigned to each first entity which is valid only for mailorder, telephone order, or internet transactions, and which is used formultiple transactions with multiple merchants.
 22. A method as recitedin claim 21, wherein the second entity uses the SCN to authenticate thefirst entity.
 23. A method for providing one or more secure transactionsbetween a first entity and at least one additional entity, comprisingthe steps of: (1) using an electronic card to generate a Secure CardNumber (“SCN”) for the first entity, wherein the SCN is comprised of:(a) a Transaction Information Block (“TIB”); (b) a Counter Block; and(c) an encrypted Personal Identification Number (“PIN”) Block; (2)transferring the SCN and a first entity identifier to a second entity ina first transaction; (3) transferring the SCN and the first entityidentifier from the second entity to a money source; and (4) verifyingthat the first transaction is valid with the money source by use of thefirst entity identifier and the SCN; wherein the TIB is used forinvoking one or more restrictions on use of the SCN; and wherein the SCNis transferred to the money source in an account number and the firstentity identifier is transferred to the money source in a non-accountdata field.
 24. A method for providing one or more secure transactionsbetween a first entity and at least one additional entity, comprisingthe steps of: (1) using an electronic card to generate a Secure CardNumber (“SCN”) for the first entity, wherein the SCN is comprised of:(a) a Transaction Information Block (“TIB”); (b) a Counter Block; and(c) an encrypted Personal Identification Number (“PIN”) Block; (2)transferring the SCN and a first entity identifier to a second entity ina first transaction; (3) transferring the SCN and the first entityidentifier from the second entity to a money source; and (4) verifyingthat the first transaction is valid with the money source by use of thefirst entity identifier and the SCN; wherein the TIB is used forinvoking one or more restrictions on use of the SCN; and wherein the SCNis readable by a magnetic card reader.
 25. A method as recited in claim24, wherein the SCN is readable from either a Track 1 or a Track 2 ofthe electronic card.
 26. A method for providing one or more securetransactions between a first entity and at least one additional entity,comprising the steps of: (1) using an electronic card to generate aSecure Card Number (“SCN”) for the first entity, wherein the SCN iscomprised of: (a) a Transaction Information Block (“TIB”); (b) a CounterBlock; and (c) an encrypted Personal Identification Number (“PIN”)Block; (2) transferring the SCN and a first entity identifier to asecond entity in a first transaction; (3) transferring the SCN and thefirst entity identifier from the second entity to a money source; and(4) verifying that the first transaction is valid with the money sourceby use of the first entity identifier and the SCN; wherein the TIB isused for invoking one or more restrictions on use of the SCN; andwherein the TIB is used by the money source to determine which of aplurality of account numbers associated with the first entity should beused for the first transaction.
 27. A method for providing a securetransaction between a first entity and a second entity comprising: (1)generating a Secure Card Number (“SCN”) for the first entity, whereinthe SCN comprises a dynamic digital signature; (2) transferring the SCNin a non-account data field and a first entity identifier in an accountdata field to a second entity in a first transaction; (3) transferringthe SCN and the first entity identifier from the second entity to amoney source; and (4) verifying that the first transaction is valid withthe money source by use of the first entity identifier and the SCN. 28.A method as recited in claim 27, wherein the first entity identifier istransferred to the money source as an account number.
 29. A method asrecited in claim 27, wherein the dynamic digital signature is formed byusing a Triple Data Encryption Standard algorithm (“TDES”).
 30. A methodas recited in claim 27, wherein the dynamic digital signature comprisesan encrypted PIN.
 31. A method as recited in claim 27, wherein thedynamic digital signature is, at least in part, encrypted, and whereinthe money source validates the SCN by duplicating a dynamic digitalsignature encryption process and by then comparing the result to thedynamic digital signature received with the first transaction.
 32. Amethod as recited in claim 27, wherein an electronic card generates theSCN.
 33. A method as recited in claim 27, wherein a PIN is entered intoan input device as a part of the generation of the SCN.
 34. A method asrecited in claim 27, wherein a unique SCN is assigned to each firstentity which is valid only for mail order, telephone order, or internettransactions, and which is used for multiple transactions with multiplemerchants.
 35. A method as recited in claim 27, wherein the secondentity uses the SCN to authenticate the first entity.